Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add badges field to Metadata #4900

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Add badges field to Metadata #4900

merged 1 commit into from
Oct 23, 2024

Conversation

grod220
Copy link
Contributor

@grod220 grod220 commented Oct 22, 2024

Describe your changes

Web apps are currently unable to visually distinguish certain IBC assets that represent rehypothecated tokens. Aka, Bitcoin from Osmosis or Nomic. Both of their metadata possess images of the plain Bitcoin logo.

This proto change proposes to add a new field: badges. It gives entities like the prax registry the ability to add source chain icons to the metadata of assets. Frontends can then display these badges on top of the asset icon.

Issue ticket number and link

penumbra-zone/web#1864
prax-wallet/registry#97

Checklist before requesting a review

  • (not relevant) I have added guiding text to explain how a reviewer should test these changes.

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    Only a protobuf schema update

Copy link
Contributor

@cronokirby cronokirby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@cronokirby cronokirby merged commit c23270b into main Oct 23, 2024
14 checks passed
@cronokirby cronokirby deleted the pb-metadata-badges branch October 23, 2024 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants